-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: remove mentioning of not spec'ed Route Broadcasting Protocol #597
base: main
Are you sure you want to change the base?
Conversation
@@ -38,7 +38,7 @@ Connectors provide a service of forwarding packets and relaying money, and they | |||
|
|||
Like the Internet protocol stack that inspired it, the Interledger protocol suite is divided into layers of protocols with different responsibilities. Lower-level protocols provide basic functionality that higher-level protocols depend on to provide more complex functionality. | |||
|
|||
> **Aside:** Not pictured in the diagram are configuration protocols including [IL-RFC-31: Interledger Dynamic Configuration Protocol](../0031-dynamic-configuration-protocol/0031-dynamic-configuration-protocol.md) and **Route Broadcasting Protocol**. These protocols are built on top of the Interledger Protocol layer and support it, but are not considered to be transport or application-layer protocols. | |||
> **Aside:** Not pictured in the diagram are configuration protocols including [IL-RFC-31: Interledger Dynamic Configuration Protocol](../0031-dynamic-configuration-protocol/0031-dynamic-configuration-protocol.md) or a route broadcasting protocol (not specified yet). These protocols are built on top of the Interledger Protocol layer and support it, but are not considered to be transport or application-layer protocols. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made it generic and pointed out that it wasn't spec'ed out yet
- Nodes are connected to each other and the relationship between two nodes is either: | ||
- `parent` and `child` (one node is the `parent` of another node that is relatively its `child`), or, | ||
- `peer` and `peer` (two nodes are peered with one another). | ||
|
||
## Overview | ||
Interledger is a protocol suite that consists of several protocols including the [Bilateral Transfer Protocol](../0023-bilateral-transfer-protocol/0023-bilateral-transfer-protocol.md), the Route Broadcasting Protocol and others necessary for establishment, operation and maintenance of the network. Interledger Dynamic Configuration Protocol (ILDCP) is one of these protocols. | ||
|
||
Interledger is a protocol suite that consists of several protocols including the [Bilateral Transfer Protocol](../0023-bilateral-transfer-protocol/0023-bilateral-transfer-protocol.md) or [ILP over HTTP](../0035-ilp-over-http/0035-ilp-over-http.md) and others necessary for establishment, operation and maintenance of the network. Interledger Dynamic Configuration Protocol (ILDCP) is one of these protocols. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added ILP over HTTP and removed Route Broadcasting Protocol. I did wonder what "and others necessary" would include.
0031-dynamic-configuration-protocol/0031-dynamic-configuration-protocol.md
Outdated
Show resolved
Hide resolved
0031-dynamic-configuration-protocol/0031-dynamic-configuration-protocol.md
Outdated
Show resolved
Hide resolved
…-protocol.md Co-authored-by: Max Kurapov <[email protected]>
…-protocol.md Co-authored-by: Max Kurapov <[email protected]>
- RBP is a protocol built on top of ILP, and is used for transferring routing information to build routing tables. | ||
- RBP data is put into the extensible data area of ILP packets. | ||
- A Route Broadcasting Protocol is thought to be a protocol built on top of ILP, and would be used for transferring routing information to build routing tables. | ||
- RBP data would be put into the extensible data area of ILP packets. | ||
- RBP is an idea that does not exist yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made this section hypothetical. If we want to completely remove it, we need to change the svgs and the numbering.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me, the third point is already implied by the first one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can imply that something does exist, but it is not part of the official spec but simply EXPERIMENTAL, which we can still link to. The experimental spec can link to the code.
It also did some auto cleanup. I'll highlight the 2 main changes in comments.